Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POTEL 70 - Add sentry-opentelemetry-agentless-spring module #4000

Merged
merged 28 commits into from
Dec 20, 2024

Conversation

adinauer
Copy link
Member

📜 Description

Add sentry-opentelemetry-agentless-spring module

💡 Motivation and Context

So we can bring the right version of opentelemetry-spring-boot-starter and also add a marker which can then later be detected for auto configuration.

💚 How did you test it?

📝 Checklist

  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Copy link
Contributor

github-actions bot commented Dec 18, 2024

Fails
🚫 Please consider adding a changelog entry for the next release.
Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- POTEL 70 - Add `sentry-opentelemetry-agentless-spring` module ([#4000](https://github.com/getsentry/sentry-java/pull/4000))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 7a1d3b7

Copy link
Contributor

github-actions bot commented Dec 18, 2024

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 424.38 ms 450.38 ms 26.00 ms
Size 1.65 MiB 2.31 MiB 677.12 KiB

Previous results on branch: feat/agentless-spring-module

Startup times

Revision Plain With Sentry Diff
793970c 412.59 ms 444.34 ms 31.75 ms
075e242 648.35 ms 728.38 ms 80.03 ms

App size

Revision Plain With Sentry Diff
793970c 1.65 MiB 2.31 MiB 677.05 KiB
075e242 1.65 MiB 2.31 MiB 677.07 KiB

Copy link
Collaborator

@lbloder lbloder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍
Left one suggestion and a question

options -> {
options.setDsn("...");
...
OpenTelemetryUtil.applyOpenTelemetryOptions(options, false);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed, as it is now obsolete. I suggest we do that in the #3978 PR

Comment on lines +14 to +17
api(Config.Libs.OpenTelemetry.otelSdk)
api(Config.Libs.OpenTelemetry.otelSemconv)
api(Config.Libs.OpenTelemetry.otelSemconvIncubating)
api(Config.Libs.OpenTelemetry.otelExtensionAutoconfigure)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we not depending on the sentry-opentelemetry-agentless module because of the AgentlessMarker?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I thought, it might cause more issues than save work to reuse the other agentless module here since there's very little in both currently.

Base automatically changed from feat/otel-span-strongref to 8.x.x December 20, 2024 10:49
@adinauer adinauer merged commit 0e41f35 into 8.x.x Dec 20, 2024
15 of 16 checks passed
@adinauer adinauer deleted the feat/agentless-spring-module branch December 20, 2024 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants